Skip to content

chore(main): release 0.0.2 - #14

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--cli
Closed

chore(main): release 0.0.2#14
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--cli

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 31, 2026

Copy link
Copy Markdown

🤖 I have created a release beep boop

0.0.2 (2026-08-31)

Features

  • add api passthrough + MCP server (ported from draft CLI) (0be6386)
  • auth: API-key-only authentication (#11) (719b209)
  • auth: PKCE browser login flow (no token in the URL) (bbce7ea)
  • cli: add keys and usage commands over console internal API (e72266f)
  • cli: agent-first output, OS-keychain storage, api-key login (8a7d060)
  • cli: fetch one voice with voices get (#7) (7d607e5)
  • cli: stream long-form speech with say --stream (#6) (ad1f436)
  • cli: voices list filters + whoami identity and --check (bac764d)
  • console-user auth + workspace context (foundation) (#1) (807f76e)
  • Speechify CLI v1 — auth, say, voices (bdc63c4)

Bug Fixes

  • auth: cache ID token across invocations to avoid refresh-token churn (9e2ae43)
  • cli: fail-fast filters, source-aware requires_console, doc fixes (fa4a7dd)
  • cli: harden auth, output, and networking from CLI review (a7732c1)
  • cli: harden MCP transport, file writes, auth & input from review (#12) (1cf46bf)
  • cli: use canonical bin path (drop ./ so npm keeps the bin on publish) (#15) (8146364)
  • mcp: always register TTS tools, resolve auth per call (d64b7be)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--cli branch from 5788dc1 to 3eac93c Compare August 31, 2026 13:21
@luke-speechify

Copy link
Copy Markdown
Contributor

Closing: this was generated before the 0.0.1 tag/release existed, so release-please had no anchor and walked the entire history — hence the whole-history changelog (including removed console/PKCE/keys/usage features) and the spurious 0.0.2 bump.

0.0.1 was published manually and now has a matching git tag + GitHub Release, so release-please is anchored. HEAD == 0.0.1, so there is nothing to release yet; future release PRs will start cleanly from commits after 0.0.1.

@luke-speechify
luke-speechify deleted the release-please--branches--main--components--cli branch August 31, 2026 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant